Feature/react query migration by jesusbalderramawgu · Pull Request #1629 · openedx/frontend-app-authn

jesusbalderramawgu · 2026-02-10T03:40:19Z

Description

PR to migrate this repository from Redux to React-query and React context. It closes the issue

What changed?

React context was added for client side state maintaining backward compatibility with the currents components, while Redux was changed for react query for server state management.
As it was mentioned above, the functionality was kept with changes required in some components to make it work with the new hooks. The tests were updated as well after the migration.

How Has This Been Tested?

tests were updated and some new were added.
Manual testing in the different paths, verifying that everything loads properly, also checking validations, loaders, requests.
The flow to login and register were tested successfully, I was able to see the learner dashboard with current credentials and with new users registered.

Note:
Even though the unit tests pass, there are some things that I couldn't test manually, such as

forgot password: I didn't get the email, do I need to run something to make this work?
ThirdPartyAuth component: this component has a SocialAuthProviders component but I couldn't render it, not sure what I need to render this or maybe is deprecated?
if someone knows how to test this, please let me know.

openedx-webhooks · 2026-02-10T03:40:26Z

Thanks for the pull request, @jesusbalderramawgu!

This repository is currently maintained by @openedx/2u-infinity.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
- This process (including the steps you'll need to take) is documented here.
If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

Dependencies

This PR must be merged before / after / at the same time as ...
Blockers

This PR is waiting for OEP-1234 to be accepted.
Timeline information

This PR must be merged by XX date because ...
Partner information

This is for a course on edx.org.
Supporting documentation
Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

The size and impact of the changes that it introduces
The need for product review
Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

jesusbalderramawgu · 2026-02-10T03:45:45Z

for some reason the lint is failing with the following files webpack.prod.config.js, .eslintrc.js and jest.config.js.
I will check this tomorrow

jesusbalderramawgu · 2026-02-10T03:46:22Z

assign me

jacobo-dominguez-wgu · 2026-02-10T17:25:19Z

tsconfig.json

+    "outDir": "dist"
+  },
+  "include": ["*.js", ".eslintrc.js", "src/**/*", "plugins/**/*", "jest.config.ts"],
+  "exclude": ["*.js", ".eslintrc.js", "dist", "node_modules"]


Suggested change

"exclude": ["*.js", ".eslintrc.js", "dist", "node_modules"]

"exclude": ["dist", "node_modules"]

This fixes the lint problems.

thank you Jacob, this fixed the issue

codecov · 2026-02-10T22:47:05Z

Codecov Report

❌ Patch coverage is 87.99314% with 70 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.22%. Comparing base (9b7be2a) to head (e5619f6).
⚠️ Report is 5 commits behind head on master.

Files with missing lines	Patch %	Lines
...ofiling/components/ProgressiveProfilingContext.tsx	0.00%	22 Missing and 2 partials ⚠️
...on-components/components/ThirdPartyAuthContext.tsx	64.28%	10 Missing ⚠️
src/forgot-password/ForgotPasswordPage.jsx	80.76%	5 Missing ⚠️
src/login/data/apiHook.ts	85.71%	5 Missing ⚠️
src/register/components/RegisterContext.tsx	93.50%	5 Missing ⚠️
src/common-components/PasswordField.jsx	50.00%	4 Missing ⚠️
src/register/RegistrationPage.jsx	89.47%	4 Missing ⚠️
src/reset-password/data/apiHook.ts	90.69%	4 Missing ⚠️
src/reset-password/ResetPasswordPage.jsx	94.33%	3 Missing ⚠️
src/forgot-password/data/apiHook.ts	87.50%	2 Missing ⚠️
... and 3 more

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1629      +/-   ##
==========================================
+ Coverage   87.57%   91.22%   +3.65%     
==========================================
  Files         125      108      -17     
  Lines        2309     2347      +38     
  Branches      648      667      +19     
==========================================
+ Hits         2022     2141     +119     
+ Misses        278      199      -79     
+ Partials        9        7       -2

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

…fig file added

… redux

arbrandes

Thank you for this work, Jesus! I like that tests are passing and things generally work. But beyond the inline comments and change requests I made, there are a few things to address:

1. Error responses don't show

The error responses don't seem to be rendered for the user. Take this one in master, for example:

In this branch the error response is simply not shown.

2. Some patterns are not consistent

I focused mostly on the different apiHooks.ts files: each one seems to do things slightly differently. While there is no Open edX guideline for useMutation() calls, we should pick one pattern and stick with it at least across each repository. It makes things easier to maintain. See the inline comments.

It's possible this applies elsewhere and I didn't catch it. But please keep the concept in mind.

3. Remove dead code

Please remove all dead code - basically, everything Redux - in this PR. There isn't much advantage in creating a separate PR for that and leaving a bunch of commented-out stuff in. It's fine if it's a separate commit, though.

4. Types

I'm not going to block the PR on it because the focus is on react-query, not Typescript, but wherever possible it would be much better if we replaced any with actual types, even if it's just the primitive ones. At the very least we should create a follow-up ticket to clean those up.

Again, thanks for the hard work!

arbrandes · 2026-02-11T16:01:41Z

src/forgot-password/ForgotPasswordPage.jsx

+          setBannerEmail(emailUsed);
+          setFormErrors('');
+        },
+        onError: () => {


You need to declare the error parameter:

Suggested change

onError: () => {

onError: (error) => {

arbrandes · 2026-02-11T16:07:05Z

src/login/components/LoginContext.tsx

+  error: string | null;
+  setError: (error: string | null) => void;
+  isLoading: boolean;
+  setIsLoading: (isLoading: boolean) => void;


The implementation of the context value below is completely different from this type. Please fix it.

arbrandes · 2026-02-11T16:09:54Z

src/logistration/Logistration.jsx

I know this was here before your PR, but this is as good an opportunity to fix it as any. If we don't add a dependency array, this will request a new CSRF token on every render:

Suggested change

}, []);

I didn't see this, good catch. Fixed!

arbrandes · 2026-02-11T16:14:55Z

src/register/RegistrationPage.jsx

+  });
+
+  const registrationErrorCode = registrationError?.errorCode || backendRegistrationError?.errorCode;
+  const submitState = registrationMutation.isLoading ? PENDING_STATE : DEFAULT_STATE;


Are you sure we don't mean isPending, here? See the react-query v5 migration blurb. Just checking.

Suggested change

const submitState = registrationMutation.isLoading ? PENDING_STATE : DEFAULT_STATE;

const submitState = registrationMutation.isPending ? PENDING_STATE : DEFAULT_STATE;

yeah you are right I changed this

arbrandes · 2026-02-11T16:15:41Z

src/login/api/loginApi.js

@@ -0,0 +1,35 @@
+// TODO: Delete this file


Please go ahead and delete any dead code.

arbrandes · 2026-02-11T16:38:59Z

src/register/data/api.hook.ts

@@ -0,0 +1,53 @@
+import { camelCaseObject } from '@edx/frontend-platform';


Please name this file with the same pattern as the other ones, apiHook.ts.

arbrandes · 2026-02-11T16:41:03Z

src/login/data/apiHook.ts

+  mutationFn: async (loginData: LoginData) => {
+    try {
+      return await login(loginData);
+    } catch (error) {


Any particular reason you're not using the onError pattern (which you do use elsewhere)?

arbrandes · 2026-02-11T16:49:41Z

src/register/data/api.hook.ts

+
+const useRegistration = (options = {}) => useMutation({
+  mutationFn: (registrationPayload) => registerNewUserApi(registrationPayload),
+  onSuccess: (data) => {


Here you are using onSuccess and onError outside the mutationFn, which is different to how you do it elsewhere. We should settle on a pattern and use it consistently everywhere, for ease of maintenance.

arbrandes · 2026-02-11T16:52:42Z

src/register/data/api.hook.ts

+import { getFieldsValidations, registerNewUserApi } from './api.ts';
+import { INTERNAL_SERVER_ERROR } from './constants';
+
+const useRegistration = (options = {}) => useMutation({


Please add a type to the options, like you do for progressive-profiling.

arbrandes · 2026-02-11T17:00:36Z

src/login/tests/LoginPage.test.jsx

-    ));
-    expect(store.dispatch).not.toHaveBeenCalledWith(loginRequest({}));
+    fireEvent.click(screen.getByRole('button', { name: /sign in/i }));
+    expect(props.loginRequest).not.toHaveBeenCalled();


We shouldn't be testing the Redux stuff, anymore.

arbrandes · 2026-02-11T18:00:08Z

Ah, and I forgot one thing: please try not to reduce coverage, both at the diff level and project level.

jesusbalderramawgu · 2026-02-12T04:15:58Z

Thank you for this work, Jesus! I like that tests are passing and things generally work. But beyond the inline comments and change requests I made, there are a few things to address:

1. Error responses don't show

The error responses don't seem to be rendered for the user. Take this one in master, for example:
In this branch the error response is simply not shown.
2. Some patterns are not consistent

I focused mostly on the different apiHooks.ts files: each one seems to do things slightly differently. While there is no Open edX guideline for useMutation() calls, we should pick one pattern and stick with it at least across each repository. It makes things easier to maintain. See the inline comments.

It's possible this applies elsewhere and I didn't catch it. But please keep the concept in mind.

3. Remove dead code

Please remove all dead code - basically, everything Redux - in this PR. There isn't much advantage in creating a separate PR for that and leaving a bunch of commented-out stuff in. It's fine if it's a separate commit, though.

4. Types

I'm not going to block the PR on it because the focus is on react-query, not Typescript, but wherever possible it would be much better if we replaced any with actual types, even if it's just the primitive ones. At the very least we should create a follow-up ticket to clean those up.

Again, thanks for the hard work!

Thank you Adolfo for your feedback, I pushed more changes to the branch.

Thank you for this work, Jesus! I like that tests are passing and things generally work. But beyond the inline comments and change requests I made, there are a few things to address:

1. Error responses don't show

The error responses don't seem to be rendered for the user. Take this one in master, for example:
In this branch the error response is simply not shown.
2. Some patterns are not consistent

I focused mostly on the different apiHooks.ts files: each one seems to do things slightly differently. While there is no Open edX guideline for useMutation() calls, we should pick one pattern and stick with it at least across each repository. It makes things easier to maintain. See the inline comments.

It's possible this applies elsewhere and I didn't catch it. But please keep the concept in mind.

3. Remove dead code

Please remove all dead code - basically, everything Redux - in this PR. There isn't much advantage in creating a separate PR for that and leaving a bunch of commented-out stuff in. It's fine if it's a separate commit, though.

4. Types

I'm not going to block the PR on it because the focus is on react-query, not Typescript, but wherever possible it would be much better if we replaced any with actual types, even if it's just the primitive ones. At the very least we should create a follow-up ticket to clean those up.

Again, thanks for the hard work!

Thank you Adolfo for your feedback, I pushed more changes to this branch.
the error responses were not correctly on the login but in the registration page were correct, not sure if I'm doing the same as you.
The loginPage was wrong I wasn't matching correctly the errorCode.type that is used in the component and it wasn't showing the proper errors, now this is fixed.

I refactored the apiHooks and renamed the ones that were incorrect.

I have deleted the redux code!

I have added types to the ones that I know what I expect.

Also I made extra changes removing unnecessary code.

Anything please let me know and again thank you so much!

jesusbalderramawgu · 2026-02-12T04:17:49Z

Ah, and I forgot one thing: please try not to reduce coverage, both at the diff level and project level.

thanks for this comment, yeah I fixed the existing ones and added new ones for the new code, but also I deleted the ones related to redux. I will check this tomorrow and I will add more tests to get the correct coverage

…ms, renaming of files

arbrandes

Ok, I can confirm the error handling bug is fixed, thanks! Thank you for addressing my comments, otherwise: the hooks refactor looks great!

There are still changes to make, however. For instance:

Please don't disable the exhaustive-deps linting rules. I know there are some stable objects that wouldn't change, but better to be explicit than implicit. If the dependencies are too big, then the contexts need to be split up.

arbrandes · 2026-02-12T21:14:20Z

package.json

Please remove the redux dependencies as well. There might be others I didn't mark: if so, remove them too.

arbrandes · 2026-02-12T21:16:54Z

src/MainApp.jsx


 registerIcons();

+const queryClient = new QueryClient();


Auth-related mutations (login, registration) probably should not retry on failure — a failed login retried 3 times would be confusing. Maybe something like:

Suggested change

const queryClient = new QueryClient();

const queryClient = new QueryClient({

defaultOptions: {

mutations: { retry: false },

},

});

arbrandes · 2026-02-12T21:20:19Z

src/register/components/RegisterContext.tsx

+    setRegistrationResult,
+    setBackendCountryCode,
+    setRegistrationError,
+  // eslint-disable-next-line react-hooks/exhaustive-deps


It should not be necessary to disable any eslint warnings. If the context is too big, let's split it up. Let's try splitting into at least RegistrationFormContext and RegistrationValidationContext.

I agree with this, I'm just concern splitting this into two contexts right now, basically I just moved the redux state into react context, didn't make any refactor. I think we can make a refactor later maybe when I work on the frontend-base update. what do you think?
by now what I did was to do a mini refactor to remove some properties that are not required in the context and move it into the local state. Also I have the useReducer and useCallback getting stable references avoiding unnecessary re renders, now it is shorter and removed the eslint warning. Looks better

Agreed, thanks!

arbrandes · 2026-02-12T21:36:20Z

src/recommendations/RecommendationsPage.jsx

  const location = useLocation();

-  const registrationResponse = location.state?.registrationResult;
+  // const registrationResponse = location.state?.registrationResult;


There's still some commented out stuff.

arbrandes · 2026-02-12T21:36:40Z

src/recommendations/RecommendationsPage.jsx

  const userId = location.state?.userId;

-  const userCountry = useSelector((state) => state.register.backendCountryCode);
+  //  const userCountry = useSelector((state) => state.register.backendCountryCode);


arbrandes · 2026-02-12T21:37:35Z

src/register/RegistrationFields/CountryField/CountryField.jsx

Remove reference to redux.

arbrandes · 2026-02-12T21:39:45Z

tsconfig.json

+{
+  "extends": "@edx/typescript-config",
+  "compilerOptions": {
+    "baseUrl": "./src",


Don't use baseUrl, please. Use rootDir instead.

arbrandes · 2026-02-12T21:49:47Z

src/login/LoginPage.jsx

+      setErrorCode({
        type: INVALID_FORM,
-        count: prevState.count + 1,
+        count: errorCode.count + 1,


This is not right. You cannot use errorCode directly, here. You're basically using a stale reference. You should, instead:

setErrorCode(prev => ({ type: INVALID_FORM, count: prev.count + 1, context: {}, }));

arbrandes · 2026-02-12T21:50:48Z

src/login/LoginPage.jsx

+    onError: (formattedError) => {
+      setErrorCode({
+        type: formattedError.type,
+        count: errorCode.count + 1,


Same problem as on line 173. errorCode is a stale reference. Do something like:

setErrorCode(prev => ({ type: formattedError.type, count: prev.count + 1, context: formattedError.context, }));

jesusbalderramawgu · 2026-02-13T02:55:57Z

Ok, I can confirm the error handling bug is fixed, thanks! Thank you for addressing my comments, otherwise: the hooks refactor looks great!

There are still changes to make, however. For instance:

Please don't disable the exhaustive-deps linting rules. I know there are some stable objects that wouldn't change, but better to be explicit than implicit. If the dependencies are too big, then the contexts need to be split up.

Thank you Adolfo for your comments, I addressed the changes that you requested also the code coverage was fixed.
Anything please let me know, Thanks!

arbrandes

Thanks for bearing with me! I found a few more things to change.

arbrandes · 2026-02-13T13:02:55Z

src/common-components/PasswordField.jsx

+    setValidationsFailure,
+    validationApiRateLimited,
+    clearRegistrationBackendError,
+  } = useRegisterContext();


The context is not always available. For example, from ResetPasswordPage. If somebody clicks on a /password_reset_confirm/ link, this will throw an exception. The tests are only passing because they wrap the page with the provider, but this is not the case in the app itself.

In other words... probably use RegisterProvider in ResetPasswordPage.

yeah, it should be there, for some reason I deleted it. now I added the provider again.
But in the future we should refactor this PasswordField I guess to avoid dependency with this context and make it more generic

arbrandes · 2026-02-13T13:09:43Z

src/recommendations/RecommendationsPage.jsx

  const { formatMessage } = useIntl();
  const isExtraSmall = useMediaQuery({ maxWidth: breakpoints.extraSmall.maxWidth - 1 });
+  const {
+    registrationResult,


registrationResult doesn't exist in useRegisterContext(). The user will always be redirected to the dashboard, below.

ProgressiveProfiling gets this from the route (via useLocation()). Maybe do the same here?

in this case I brought the registrationResult back to the register context, because it takes the url when a user registers and other data. that's why it was in the context in first place, I missed this last night.
Maybe this is a refactor for the next step

arbrandes · 2026-02-13T13:13:35Z

src/reset-password/ResetPasswordPage.jsx

+  if (status === TOKEN_STATE.PENDING) {
    if (token) {
-      props.validateToken(token);
+      validateResetToken(token, {


You can't call this directly in the render function. It's going to be called on every render. This needs to be moved into a useEffect with the [token] as a dependency.

(There's some other similar weirdness on this page, but most of it was already there. This one is worth fixing now because it's using a react-query mutation.)

didn't notice, that it was directly. I made the change, thank you

arbrandes · 2026-02-13T13:22:30Z

src/logistration/Logistration.jsx

 };

-Logistration.defaultProps = {
-  selectedPage: REGISTER_PAGE,


Without this default, the register page in MainApp.jsx needs an explicit selectedPage, too.

arbrandes · 2026-02-13T13:23:19Z

src/MainApp.jsx

+            <UnAuthOnlyRoute><Logistration selectedPage={LOGIN_PAGE} /></UnAuthOnlyRoute>
+          }
+        />
+        <Route path={REGISTER_PAGE} element={<UnAuthOnlyRoute><Logistration /></UnAuthOnlyRoute>} />


Needs an explicit selected page now that the default is gone:

Suggested change

<Route path={REGISTER_PAGE} element={<UnAuthOnlyRoute><Logistration /></UnAuthOnlyRoute>} />

<Route path={REGISTER_PAGE} element={<UnAuthOnlyRoute><Logistration selectedPage={REGISTER_PAGE} /></UnAuthOnlyRoute>} />

arbrandes · 2026-02-13T13:26:08Z

src/common-components/data/apiHook.ts

+// Error constants
+export const THIRD_PARTY_AUTH_ERROR = 'third-party-auth-error';
+
+const useThirdPartyAuthHook = () => useMutation({


Why use a mutation for a GET request?

you are right, I made the change

arbrandes · 2026-02-13T13:27:32Z

src/forgot-password/data/apiHook.ts

+    forgotPassword(email)
+  ),
+  onSuccess: (data: ForgotPasswordResult, email: string) => {
+    logInfo(`Forgot password email sent to ${email}`);


We shouldn't be logging user's emails. Was the code doing this before?

this was my mistake I removed it

arbrandes · 2026-02-13T13:28:34Z

src/reset-password/ResetPasswordPage.jsx

@@ -207,18 +245,4 @@ ResetPasswordPage.defaultProps = {
  errorMsg: null,
 };


These aren't needed anymore, right?

arbrandes · 2026-02-13T13:29:50Z

src/forgot-password/ForgotPasswordPage.jsx

-  status: null,
-  submitState: DEFAULT_STATE,
-};
+ForgotPasswordPage.defaultProps = {};


We don't need defaultProps at all, no?

arbrandes · 2026-02-13T13:30:07Z

src/forgot-password/ForgotPasswordPage.jsx

-  status: PropTypes.string,
-  submitState: PropTypes.string,
-};
+ForgotPasswordPage.propTypes = {};


I don't think we need this, anymore.

jesusbalderramawgu · 2026-02-13T19:15:31Z

Thanks for bearing with me! I found a few more things to change.

Thank you Adolfo, I addressed the other comments

openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Feb 10, 2026

openedx-webhooks added this to Contributions Feb 10, 2026

github-project-automation bot moved this to Needs Triage in Contributions Feb 10, 2026

github-actions bot assigned jesusbalderramawgu Feb 10, 2026

mphilbrick211 added the mao-onboarding Reviewing this will help onboard devs from an Axim mission-aligned organization (MAO). label Feb 10, 2026

mphilbrick211 moved this from Needs Triage to Waiting on Author in Contributions Feb 10, 2026

jacobo-dominguez-wgu reviewed Feb 10, 2026

View reviewed changes

jesusbalderramawgu added 10 commits February 10, 2026 18:40

feat: first part of the migration from redux to react query

f8e5d29

fix: fix login

4287ac7

fix: tests fixed and new ones added, missing packages added and tscon…

36d2da7

…fig file added

fix: LoginProvider added to keep functionality in form like it was in…

37b50f7

… redux

fix: tests fix and lintern

cba425d

fix: lint fix and renaming

f345f83

fix: final adjustments and minor fixes

3e9936f

chore: cleanup

f6f2c90

fix: tsconfig fixed

28c90ea

fix: missing test skipped it

6b4d629

jesusbalderramawgu force-pushed the feature/react-query-migration branch from 0428d62 to 6b4d629 Compare February 11, 2026 00:41

arbrandes linked an issue Feb 11, 2026 that may be closed by this pull request

[react-query] Convert from redux to react-query #1621

Open

arbrandes mentioned this pull request Feb 11, 2026

[react-query] Convert from redux to react-query #1621

Open

arbrandes requested changes Feb 11, 2026

View reviewed changes

arbrandes mentioned this pull request Feb 11, 2026

React query and react context conversion openedx/frontend-app-learner-dashboard#786

Open

fix: refactor to keep consistency in hooks, correct validation in for…

ae4662c

…ms, renaming of files

jesusbalderramawgu added 2 commits February 11, 2026 22:24

fix: lint and tests fix

f08af81

chore: redux clean up after migration

d999091

jesusbalderramawgu force-pushed the feature/react-query-migration branch from bb02894 to d999091 Compare February 12, 2026 04:26

jesusbalderramawgu added 2 commits February 11, 2026 22:47

fix: remove missing redux data

9ec982d

fix: missing tests added to improve coverage

8031769

arbrandes requested changes Feb 12, 2026

View reviewed changes

jesusbalderramawgu added 3 commits February 12, 2026 16:50

fix: tests added

7eab2e5

fix: more references to redux deleted and comments

ae51146

fix: refactor in registerContext

62dc858

jesusbalderramawgu requested a review from arbrandes February 13, 2026 02:56

arbrandes requested changes Feb 13, 2026

View reviewed changes

jesusbalderramawgu added 3 commits February 13, 2026 12:40

fix: refactor in apihook and context

955118f

fix: fix in form to render the fields in progressiveProfiling

1316cd9

chore: removed proptypes

b37811c

jesusbalderramawgu requested a review from arbrandes February 13, 2026 19:15

fix: correct handle of status for resetPasswordPage

e5619f6

	"exclude": ["*.js", ".eslintrc.js", "dist", "node_modules"]
	"exclude": ["dist", "node_modules"]

	const submitState = registrationMutation.isLoading ? PENDING_STATE : DEFAULT_STATE;
	const submitState = registrationMutation.isPending ? PENDING_STATE : DEFAULT_STATE;

		@@ -0,0 +1,53 @@
		import { camelCaseObject } from '@edx/frontend-platform';

-const queryClient = new QueryClient();
+const queryClient = new QueryClient({
+  defaultOptions: {
+    mutations: { retry: false },
+  },
+});

	<Route path={REGISTER_PAGE} element={<UnAuthOnlyRoute><Logistration /></UnAuthOnlyRoute>} />
	<Route path={REGISTER_PAGE} element={<UnAuthOnlyRoute><Logistration selectedPage={REGISTER_PAGE} /></UnAuthOnlyRoute>} />

		@@ -207,18 +245,4 @@ ResetPasswordPage.defaultProps = {
		errorMsg: null,
		};

Conversation

jesusbalderramawgu commented Feb 10, 2026 • edited by arbrandes Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

What changed?

How Has This Been Tested?

Uh oh!

openedx-webhooks commented Feb 10, 2026

Uh oh!

jesusbalderramawgu commented Feb 10, 2026

Uh oh!

jesusbalderramawgu commented Feb 10, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

codecov bot commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

arbrandes left a comment

Choose a reason for hiding this comment

1. Error responses don't show

2. Some patterns are not consistent

3. Remove dead code

4. Types

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

arbrandes commented Feb 11, 2026

Uh oh!

jesusbalderramawgu commented Feb 12, 2026

1. Error responses don't show

2. Some patterns are not consistent

3. Remove dead code

4. Types

1. Error responses don't show

2. Some patterns are not consistent

3. Remove dead code

4. Types

Uh oh!

jesusbalderramawgu commented Feb 12, 2026

Uh oh!

arbrandes left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

jesusbalderramawgu commented Feb 10, 2026 •

edited by arbrandes

Loading

codecov bot commented Feb 10, 2026 •

edited

Loading